Autogenerated HTML docs for v2.2.0-rc0
diff --git a/git-cat-file.html b/git-cat-file.html index ec7d90c..225bce5 100644 --- a/git-cat-file.html +++ b/git-cat-file.html
@@ -3,7 +3,7 @@ <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <head> <meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" /> -<meta name="generator" content="AsciiDoc 8.6.6" /> +<meta name="generator" content="AsciiDoc 8.6.9" /> <title>git-cat-file(1)</title> <style type="text/css"> /* Shared CSS for AsciiDoc xhtml11 and html5 backends */ @@ -87,10 +87,16 @@ ul > li { color: #aaa; } ul > li > * { color: black; } -pre { +.monospaced, code, pre { + font-family: "Courier New", Courier, monospace; + font-size: inherit; + color: navy; padding: 0; margin: 0; } +pre { + white-space: pre-wrap; +} #author { color: #527bbd; @@ -219,7 +225,7 @@ } div.imageblock div.content { padding-left: 0; } -span.image img { border-style: none; } +span.image img { border-style: none; vertical-align: text-bottom; } a.image:visited { color: white; } dl { @@ -349,7 +355,7 @@ margin-bottom: 0.1em; } -div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 { +div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 { margin-top: 0; margin-bottom: 0; } @@ -407,18 +413,14 @@ span.overline { text-decoration: overline; } span.line-through { text-decoration: line-through; } +div.unbreakable { page-break-inside: avoid; } + /* * xhtml11 specific * * */ -tt { - font-family: monospace; - font-size: inherit; - color: navy; -} - div.tableblock { margin-top: 1.0em; margin-bottom: 1.5em; @@ -452,12 +454,6 @@ * * */ -.monospaced { - font-family: monospace; - font-size: inherit; - color: navy; -} - table.tableblock { margin-top: 1.0em; margin-bottom: 1.5em; @@ -537,6 +533,8 @@ @media print { body.manpage div#toc { display: none; } } + + </style> <script type="text/javascript"> /*<+'])'); + var re = new RegExp('[hH]([1-'+(toclevels+1)+'])'); // Function that scans the DOM tree for header elements (the DOM2 // nodeIterator API would be a better technique but not supported by all // browsers). @@ -610,7 +608,7 @@ var i; for (i = 0; i < toc.childNodes.length; i++) { var entry = toc.childNodes[i]; - if (entry.nodeName == 'div' + if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") && entry.getAttribute("class").match(/^toclevel/)) tocEntriesToRemove.push(entry); @@ -656,7 +654,7 @@ var entriesToRemove = []; for (i = 0; i < noteholder.childNodes.length; i++) { var entry = noteholder.childNodes[i]; - if (entry.nodeName == 'div' && entry.getAttribute("class") == "footnote") + if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote") entriesToRemove.push(entry); } for (i = 0; i < entriesToRemove.length; i++) { @@ -849,7 +847,7 @@ <p> Print object information and contents for each object provided on stdin. May not be combined with any other options or arguments. - See the section <tt>BATCH OUTPUT</tt> below for details. + See the section <code>BATCH OUTPUT</code> below for details. </p> </dd> <dt class="hdlist1"> @@ -862,7 +860,7 @@ <p> Print object information for each object provided on stdin. May not be combined with any other options or arguments. See the - section <tt>BATCH OUTPUT</tt> below for details. + section <code>BATCH OUTPUT</code> below for details. </p> </dd> </dl></div> @@ -882,17 +880,17 @@ <div class="sect1"> <h2 id="_batch_output">BATCH OUTPUT</h2> <div class="sectionbody"> -<div class="paragraph"><p>If <tt>--batch</tt> or <tt>--batch-check</tt> is given, <tt>cat-file</tt> will read objects +<div class="paragraph"><p>If <code>--batch</code> or <code>--batch-check</code> is given, <code>cat-file</code> will read objects from stdin, one per line, and print information about them. By default, the whole line is considered as an object, as if it were fed to <a href="git-rev-parse.html">git-rev-parse(1)</a>.</p></div> <div class="paragraph"><p>You can specify the information shown for each object by using a custom -<tt><format></tt>. The <tt><format></tt> is copied literally to stdout for each -object, with placeholders of the form <tt>%(atom)</tt> expanded, followed by a +<code><format></code>. The <code><format></code> is copied literally to stdout for each +object, with placeholders of the form <code>%(atom)</code> expanded, followed by a newline. The available atoms are:</p></div> <div class="dlist"><dl> <dt class="hdlist1"> -<tt>objectname</tt> +<code>objectname</code> </dt> <dd> <p> @@ -900,43 +898,43 @@ </p> </dd> <dt class="hdlist1"> -<tt>objecttype</tt> +<code>objecttype</code> </dt> <dd> <p> - The type of of the object (the same as <tt>cat-file -t</tt> reports). + The type of of the object (the same as <code>cat-file -t</code> reports). </p> </dd> <dt class="hdlist1"> -<tt>objectsize</tt> +<code>objectsize</code> </dt> <dd> <p> - The size, in bytes, of the object (the same as <tt>cat-file -s</tt> + The size, in bytes, of the object (the same as <code>cat-file -s</code> reports). </p> </dd> <dt class="hdlist1"> -<tt>objectsize:disk</tt> +<code>objectsize:disk</code> </dt> <dd> <p> The size, in bytes, that the object takes up on disk. See the - note about on-disk sizes in the <tt>CAVEATS</tt> section below. + note about on-disk sizes in the <code>CAVEATS</code> section below. </p> </dd> <dt class="hdlist1"> -<tt>deltabase</tt> +<code>deltabase</code> </dt> <dd> <p> If the object is stored as a delta on-disk, this expands to the 40-hex sha1 of the delta base object. Otherwise, expands to the - null sha1 (40 zeroes). See <tt>CAVEATS</tt> below. + null sha1 (40 zeroes). See <code>CAVEATS</code> below. </p> </dd> <dt class="hdlist1"> -<tt>rest</tt> +<code>rest</code> </dt> <dd> <p> @@ -944,31 +942,31 @@ at the first whitespace boundary. All characters before that whitespace are considered to be the object name; characters after that first run of whitespace (i.e., the "rest" of the - line) are output in place of the <tt>%(rest)</tt> atom. + line) are output in place of the <code>%(rest)</code> atom. </p> </dd> </dl></div> -<div class="paragraph"><p>If no format is specified, the default format is <tt>%(objectname) -%(objecttype) %(objectsize)</tt>.</p></div> -<div class="paragraph"><p>If <tt>--batch</tt> is specified, the object information is followed by the -object contents (consisting of <tt>%(objectsize)</tt> bytes), followed by a +<div class="paragraph"><p>If no format is specified, the default format is <code>%(objectname) +%(objecttype) %(objectsize)</code>.</p></div> +<div class="paragraph"><p>If <code>--batch</code> is specified, the object information is followed by the +object contents (consisting of <code>%(objectsize)</code> bytes), followed by a newline.</p></div> -<div class="paragraph"><p>For example, <tt>--batch</tt> without a custom format would produce:</p></div> +<div class="paragraph"><p>For example, <code>--batch</code> without a custom format would produce:</p></div> <div class="listingblock"> <div class="content"> -<pre><tt><sha1> SP <type> SP <size> LF -<contents> LF</tt></pre> +<pre><code><sha1> SP <type> SP <size> LF +<contents> LF</code></pre> </div></div> -<div class="paragraph"><p>Whereas <tt>--batch-check='%(objectname) %(objecttype)'</tt> would produce:</p></div> +<div class="paragraph"><p>Whereas <code>--batch-check='%(objectname) %(objecttype)'</code> would produce:</p></div> <div class="listingblock"> <div class="content"> -<pre><tt><sha1> SP <type> LF</tt></pre> +<pre><code><sha1> SP <type> LF</code></pre> </div></div> <div class="paragraph"><p>If a name is specified on stdin that cannot be resolved to an object in -the repository, then <tt>cat-file</tt> will ignore any custom format and print:</p></div> +the repository, then <code>cat-file</code> will ignore any custom format and print:</p></div> <div class="listingblock"> <div class="content"> -<pre><tt><object> SP missing LF</tt></pre> +<pre><code><object> SP missing LF</code></pre> </div></div> </div> </div>